Date: Tue, 19 Jul 94 04:30:01 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.Edu Reply-To: TCP-Group@UCSD.Edu Precedence: Bulk Subject: TCP-Group Digest V94 #152 To: tcp-group-digest TCP-Group Digest Tue, 19 Jul 94 Volume 94 : Issue 152 Today's Topics: dama in wnos4a8 unexpected text connections Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Mon, 18 Jul 94 13:36:55 EST From: BARRY TITMARSH Subject: dama in wnos4a8 To: dl1bke , TCP-GROUP More info. I found a mistake typo in ax25route.c where i did not /* out */ a short line else if ( /* cp->rejsent && */ (cp->reseq ..... im shure you know where.. well this did not fix the problem. Im connecting with tests to db0dar the darmstadt Germany flexnet-dama digi its almost impossible to get a ax25 trace as the system just stops as soon as i get an I frame ?? well i think thats it.. i see my SAMB go out and the UA (dama) come back, at this poing it just crashes the NOS. again im thinking that there is a small part of the code in error the dama processing of I frames. ? any one else want to have the src code and help work on this bug ?? please email me an ill mail you the src's some help please.. Thanks. Barry gm8sau/dc0hk ------------------------------ Date: Mon, 18 Jul 1994 14:09:09 -0700 From: brian@nothing.UCSD.EDU (Brian Kantor) Subject: unexpected text connections To: tcp-group@ucsd.edu If I have a process accepting AX.25 connections with the expectation that imbedded protocols (tcp/ip, net/rom, etc) will be passed up to the next protocol layer, but I don't have a text stream listener waiting on the socket, what should I do when streamtext comes along? Reply with a 'service not available' or 'no handler attached' message, and/or disconnect? Where this happens is when a naive vanilla AX.25 user connects to a port that's not normally configured to handle vanilla streamtext connections. Just tossing the packet on the ground is uncool; it leaves the user wondering whether his equipment has died or what. Or should an unattached streamtext socket become an echo server? That is, the naive user would just get back everything he sends? Suggestions? - Brian ------------------------------ End of TCP-Group Digest V94 #152 ******************************